System, method and article of manufacture for a network-based child support framework

ABSTRACT

A system, method and article of manufacture are provided for providing a network-based child financial support framework. First, a database is maintained including information on a received financial support payment utilizing a network. Further, general information is provided relating to the financial support payment utilizing the network. The calculation of a proper amount of the financial support payment may also be allowed based on a profile a user. Still yet, a history associated with the financial support payment is displayed.

This application is a continuation of U.S. patent application Ser. No.09/560,665, filed Apr. 27, 2000 now U.S. Pat. No. 7,716,059, the entirecontents of which are incorporated herein by reference.

FIELD OF THE INVENTION

The present invention relates to databases and more particularly todatabases for tracking parental financial support.

BACKGROUND OF THE INVENTION

Currently, child support systems rely heavily on telephonic or in-personcommunications between custodial and non-custodial parents and stateagency staff. Even simple questions about such things as status ofsupport payments have to be answered by talking to a staff member withdedicated computer terminals connected directly to intra-agency computersystems, resulting in the custodial parents having very little activeparticipation in the management of their cases.

Parents and state staff members also rely on mail to communicate.However, correspondence sent through the postal system is slow and mayget lost. Further, postage costs place a heavy burden on alreadystrained budgets.

What is needed is a system that allows parents involved in a childsupport case to access information immediately without speaking directlyto a state agency staff member or waiting for correspondence.

SUMMARY OF THE INVENTION

A system, method and article of manufacture are provided for providing anetwork-based child financial support framework. First, a database ismaintained including information on a received financial support paymentutilizing a network. Further, general information is provided relatingto the financial support payment utilizing the network. The calculationof a proper amount of the financial support payment may also be allowedbased on a profile a user. Still yet, a history associated with thefinancial support payment is displayed.

In one embodiment of the present invention, the profile may include datasuch as income, number of children, basic support, insurance premium,child care cost, and/or additional expenses. The history may include adate, an amount received on the date, an amount retained of the amountreceived, and a disbursement of the amount received to the custodialparent.

In yet another embodiment of the present invention, a plurality offrequently asked questions may be presented relating to the financialsupport payment.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood when consideration is given tothe following detailed description thereof. Such description makesreference to the annexed drawings wherein:

FIG. 1 is a flowchart illustrating a method for providing anetwork-based child financial support framework;

FIG. 1A illustrates an exemplary network architecture for implementingthe present invention;

FIG. 2 is a schematic diagram of a hardware implementation of oneembodiment of the present invention;

FIG. 3 illustrates a home page interface in accordance with oneembodiment of the present invention;

FIG. 4 is a flowchart illustrating a method for affording informationservices in a child support framework;

FIG. 5 is a graphical user interface illustrating the frequently askedquestions associated with the information services of FIG. 4;

FIG. 6 is a graphical user interface illustrating the financial supportviolators associated with the information services of FIG. 4;

FIG. 7 is a graphical user interface illustrating the field office linksassociated with the information services of FIG. 4;

FIG. 8 is a graphical user interface illustrating other servicesassociated with the information services of FIG. 4;

FIG. 9 is a graphical user interface illustrating the eligibilityrequirements associated with the receiving financial support of FIG. 4;

FIG. 10 is a flowchart illustrating a method for affording a financialsupport payment status;

FIG. 11 is a log-in graphical user interface that may be required forexecution of the method of FIG. 10;

FIG. 12 is a graphical user interface that allows access to varioustypes of status information in accordance with the method of FIG. 10;

FIG. 13 is a flowchart illustrating a method for providing a paymenthistory of a financial support payment;

FIG. 14 is a graphical user interface that conveys the payment historyinformation in accordance with the method of FIG. 13;

FIG. 15 is a flowchart of a method for calculating an amount of childsupport;

FIG. 16 is a graphical user interface that executes the calculatorfunction in accordance with the method of FIG. 15;

FIG. 17 is a summary of a proposed site map associated with the presentinvention;

FIGS. 18-24 show flow diagrams illustrating possible navigation routesduring use of the present invention;

FIG. 25 illustrates the components of the “25 Most Wanted”Infrastructure;

FIG. 26 illustrates the “Recent News on Case” Infrastructure Components;

FIG. 27 illustrates the Amount Due For The Current Month InfrastructureComponents;

FIG. 28 is a “Contact Us/Email Connection to Case Worker” InfrastructureComponents;

FIG. 29 illustrates the components of the “Have You Found theNon-Custodial Parent of My Children” Infrastructure;

FIG. 30 illustrates the components of the “Where is My Money”Infrastructure; and

FIG. 31 illustrates the “Why Didn't I Get My Child Support Payment”Infrastructure Components.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention provides an eChild Support Enforcementintention-based, interactive web application that allows parents andemployers to exchange information that previously could only be handledon the phone or in person with state agency staff. Using anintention-based question/answer based approach, eChild SupportEnforcement lets case participants inquire about the status of theirsupport cases. Thus, custodial and non-custodial parents are allowedaccess to information which was previously only available to speciallytrained state agency staff using dedicated computer terminals connecteddirectly to intra-agency computer systems. The application activelyengages custodial parents in the management of their cases. The eChildSupport Enforcement application provides better methods and toolsallowing the custodial parent and the case worker to share information.

FIG. 1 is a flowchart illustrating a method 100 for providing anetwork-based child financial support framework. First, in operation102, a database is maintained including information on a receivedfinancial support payment utilizing a network. Further, in operation104, general information is provided relating to the financial supportpayment utilizing the network. The calculation of a proper amount of thefinancial support payment may also be allowed based on a profile a user,as indicated in operation 106. Still yet, in operation 108, a historyassociated with the financial support payment is displayed.

FIG. 1A illustrates an exemplary network architecture 150 forimplementing the present invention. As shown, a web browser 152 is usedto connect to a web server 154. The web server is connected to anapplication server 156 and a mainframe 158. The various components setforth in FIG. 1A may be practiced in the context of a personal computersuch as an IBM compatible personal computer, Apple Macintosh computer orUNIX based workstation. A representative hardware environment isdepicted in FIG. 2, which illustrates a typical hardware configurationof a workstation in accordance with a preferred embodiment having acentral processing unit 210, such as a microprocessor, and a number ofother units interconnected via a system bus 212. The workstation shownin FIG. 2 includes a Random Access Memory (RAM) 214, Read Only Memory(ROM) 216, an I/O adapter 218 for connecting peripheral devices such asdisk storage units 220 to the bus 212, a user interface adapter 222 forconnecting a keyboard 224, a mouse 226, a speaker 228, a microphone 232,and/or other user interface devices such as a touch screen (not shown)to the bus 212, communication adapter 234 for connecting the workstationto a communication network (e.g., a data processing network) and adisplay adapter 236 for connecting the bus 212 to a display device 238.The workstation typically has resident thereon an operating system suchas the Microsoft Windows NT or Windows/95 Operating System (OS), the IBMOS/2 operating system, the MAC OS, or UNIX operating system. Thoseskilled in the art will appreciate that the present invention may alsobe implemented on platforms and operating systems other than thosementioned.

A preferred embodiment is written using JAVA, C, and the C++ languageand utilizes object oriented programming methodology. Object orientedprogramming (OOP) has become increasingly used to develop complexapplications. As OOP moves toward the mainstream of software design anddevelopment, various software solutions require adaptation to make useof the benefits of OOP. A need exists for these principles of OOP to beapplied to a messaging interface of an electronic messaging system suchthat a set of OOP classes and objects for the messaging interface can beprovided.

OOP is a process of developing computer software using objects,including the steps of analyzing the problem, designing the system, andconstructing the program. An object is a software package that containsboth data and a collection of related structures and procedures. Sinceit contains both data and a collection of structures and procedures, itcan be visualized as a self-sufficient component that does not requireother additional structures, procedures or data to perform its specifictask. OOP, therefore, views a computer program as a collection oflargely autonomous components, called objects, each of which isresponsible for a specific task. This concept of packaging data,structures, and procedures together in one component or module is calledencapsulation.

In general, OOP components are reusable software modules which presentan interface that conforms to an object model and which are accessed atrun-time through a component integration architecture. A componentintegration architecture is a set of architecture mechanisms which allowsoftware modules in different process spaces to utilize each otherscapabilities or functions. This is generally done by assuming a commoncomponent object model on which to build the architecture. It isworthwhile to differentiate between an object and a class of objects atthis point. An object is a single instance of the class of objects,which is often just called a class. A class of objects can be viewed asa blueprint, from which many objects can be formed.

OOP allows the programmer to create an object that is a part of anotherobject. For example, the object representing a piston engine is said tohave a composition-relationship with the object representing a piston.In reality, a piston engine comprises a piston, valves and many othercomponents; the fact that a piston is an element of a piston engine canbe logically and semantically represented in OOP by two objects.

OOP also allows creation of an object that “depends from” anotherobject. If there are two objects, one representing a piston engine andthe other representing a piston engine wherein the piston is made ofceramic, then the relationship between the two objects is not that ofcomposition. A ceramic piston engine does not make up a piston engine.Rather it is merely one kind of piston engine that has one morelimitation than the piston engine; its piston is made of ceramic. Inthis case, the object representing the ceramic piston engine is called aderived object, and it inherits all of the aspects of the objectrepresenting the piston engine and adds further limitation or detail toit. The object representing the ceramic piston engine “depends from” theobject representing the piston engine. The relationship between theseobjects is called inheritance.

When the object or class representing the ceramic piston engine inheritsall of the aspects of the objects representing the piston engine, itinherits the thermal characteristics of a standard piston defined in thepiston engine class. However, the ceramic piston engine object overridesthese ceramic specific thermal characteristics, which are typicallydifferent from those associated with a metal piston. It skips over theoriginal and uses new functions related to ceramic pistons. Differentkinds of piston engines have different characteristics, but may have thesame underlying functions associated with it (e.g., how many pistons inthe engine, ignition sequences, lubrication, etc.). To access each ofthese functions in any piston engine object, a programmer would call thesame functions with the same names, but each type of piston engine mayhave different/overriding implementations of functions behind the samename. This ability to hide different implementations of a functionbehind the same name is called polymorphism and it greatly simplifiescommunication among objects.

With the concepts of composition-relationship, encapsulation,inheritance and polymorphism, an object can represent just aboutanything in the real world. In fact, one's logical perception of thereality is the only limit on determining the kinds of things that canbecome objects in object-oriented software. Some typical categories areas follows:

-   -   Objects can represent physical objects, such as automobiles in a        traffic-flow simulation, electrical components in a        circuit-design program, countries in an economics model, or        aircraft in an air-traffic-control system.    -   Objects can represent elements of the computer-user environment        such as windows, menus or graphics objects.    -   An object can represent an inventory, such as a personnel file        or a table of the latitudes and longitudes of cities.    -   An object can represent user-defined data types such as time,        angles, and complex numbers, or points on the plane.

With this enormous capability of an object to represent just about anylogically separable matters, OOP allows the software developer to designand implement a computer program that is a model of some aspects ofreality, whether that reality is a physical entity, a process, a system,or a composition of matter. Since the object can represent anything, thesoftware developer can create an object which can be used as a componentin a larger software project in the future.

If 90% of a new OOP software program consists of proven, existingcomponents made from preexisting reusable objects, then only theremaining 10% of the new software project has to be written and testedfrom scratch. Since 90% already came from an inventory of extensivelytested reusable objects, the potential domain from which an error couldoriginate is 10% of the program. As a result, OOP enables softwaredevelopers to build objects out of other, previously built objects.

This process closely resembles complex machinery being built out ofassemblies and sub-assemblies. OOP technology, therefore, makes softwareengineering more like hardware engineering in that software is builtfrom existing components, which are available to the developer asobjects. All this adds up to an improved quality of the software as wellas an increased speed of its development.

Programming languages are beginning to fully support the OOP principles,such as encapsulation, inheritance, polymorphism, andcomposition-relationship. With the advent of the C++ language, manycommercial software developers have embraced OOP. C++ is an OOP languagethat offers a fast, machine-executable code. Furthermore, C++ issuitable for both commercial-application and systems-programmingprojects. For now, C++ appears to be the most popular choice among manyOOP programmers, but there is a host of other OOP languages, such asSmalltalk, Common Lisp Object System (CLOS), and Eiffel. Additionally,OOP capabilities are being added to more traditional popular computerprogramming languages such as Pascal.

The benefits of object classes can be summarized, as follows:

-   -   Objects and their corresponding classes break down complex        programming problems into many smaller, simpler problems.    -   Encapsulation enforces data abstraction through the organization        of data into small, independent objects that can communicate        with each other. Encapsulation protects the data in an object        from accidental damage, but allows other objects to interact        with that data by calling the object's member functions and        structures.    -   Subclassing and inheritance make it possible to extend and        modify objects through deriving new kinds of objects from the        standard classes available in the system. Thus, new capabilities        are created without having to start from scratch.    -   Polymorphism and multiple inheritance make it possible for        different programmers to mix and match characteristics of many        different classes and create specialized objects that can still        work with related objects in predictable ways.    -   Class hierarchies and containment hierarchies provide a flexible        mechanism for modeling real-world objects and the relationships        among them.    -   Libraries of reusable classes are useful in many situations, but        they also have some limitations. For example:    -   Complexity. In a complex system, the class hierarchies for        related classes can become extremely confusing, with many dozens        or even hundreds of classes.    -   Flow of control. A program written with the aid of class        libraries is still responsible for the flow of control (i.e., it        must control the interactions among all the objects created from        a particular library). The programmer has to decide which        functions to call at what times for which kinds of objects.    -   Duplication of effort. Although class libraries allow        programmers to use and reuse many small pieces of code, each        programmer puts those pieces together in a different way. Two        different programmers can use the same set of class libraries to        write two programs that do exactly the same thing but whose        internal structure (i.e., design) may be quite different,        depending on hundreds of small decisions each programmer makes        along the way. Inevitably, similar pieces of code end up doing        similar things in slightly different ways and do not work as        well together as they should.

Class libraries are very flexible. As programs grow more complex, moreprogrammers are forced to reinvent basic solutions to basic problemsover and over again. A relatively new extension of the class libraryconcept is to have a framework of class libraries. This framework ismore complex and consists of significant collections of collaboratingclasses that capture both the small scale patterns and major mechanismsthat implement the common requirements and design in a specificapplication domain. They were first developed to free applicationprogrammers from the chores involved in displaying menus, windows,dialog boxes, and other standard user interface elements for personalcomputers.

Frameworks also represent a change in the way programmers think aboutthe interaction between the code they write and code written by others.In the early days of procedural programming, the programmer calledlibraries provided by the operating system to perform certain tasks, butbasically the program executed down the page from start to finish, andthe programmer was solely responsible for the flow of control. This wasappropriate for printing out paychecks, calculating a mathematicaltable, or solving other problems with a program that executed in justone way.

The development of graphical user interfaces began to turn thisprocedural programming arrangement inside out. These interfaces allowthe user, rather than program logic, to drive the program and decidewhen certain actions should be performed. Today, most personal computersoftware accomplishes this by means of an event loop which monitors themouse, keyboard, and other sources of external events and calls theappropriate parts of the programmer's code according to actions that theuser performs. The programmer no longer determines the order in whichevents occur. Instead, a program is divided into separate pieces thatare called at unpredictable times and in an unpredictable order. Byrelinquishing control in this way to users, the developer creates aprogram that is much easier to use. Nevertheless, individual pieces ofthe program written by the developer still call libraries provided bythe operating system to accomplish certain tasks, and the programmermust still determine the flow of control within each piece after it'scalled by the event loop. Application code still “sits on top of” thesystem.

Even event loop programs require programmers to write a lot of code thatshould not need to be written separately for every application. Theconcept of an application framework carries the event loop conceptfurther. Instead of dealing with all the nuts and bolts of constructingbasic menus, windows, and dialog boxes and then making these things allwork together, programmers using application frameworks start withworking application code and basic user interface elements in place.Subsequently, they build from there by replacing some of the genericcapabilities of the framework with the specific capabilities of theintended application.

Application frameworks reduce the total amount of code that a programmerhas to write from scratch. However, because the framework is really ageneric application that displays windows, supports copy and paste, andso on, the programmer can also relinquish control to a greater degreethan event loop programs permit. The framework code takes care of almostall event handling and flow of control, and the programmer's code iscalled only when the framework needs it (e.g., to create or manipulate aproprietary data structure).

A programmer writing a framework program not only relinquishes controlto the user (as is also true for event loop programs), but alsorelinquishes the detailed flow of control within the program to theframework. This approach allows the creation of more complex systemsthat work together in interesting ways, as opposed to isolated programs,having custom code, being created over and over again for similarproblems.

Thus, as is explained above, a framework basically is a collection ofcooperating classes that make up a reusable design solution for a givenproblem domain. It typically includes objects that provide defaultbehavior (e.g., for menus and windows), and programmers use it byinheriting some of that default behavior and overriding other behaviorso that the framework calls application code at the appropriate times.

There are three main differences between frameworks and class libraries:

-   -   Behavior versus protocol. Class libraries are essentially        collections of behaviors that you can call when you want those        individual behaviors in your program. A framework, on the other        hand, provides not only behavior but also the protocol or set of        rules that govern the ways in which behaviors can be combined,        including rules for what a programmer is supposed to provide        versus what the framework provides.    -   Call versus override. With a class library, the code the        programmer instantiates objects and calls their member        functions. It's possible to instantiate and call objects in the        same way with a framework (i.e., to treat the framework as a        class library), but to take full advantage of a framework's        reusable design, a programmer typically writes code that        overrides and is called by the framework. The framework manages        the flow of control among its objects. Writing a program        involves dividing responsibilities among the various pieces of        software that are called by the framework rather than specifying        how the different pieces should work together.    -   Implementation versus design. With class libraries, programmers        reuse only implementations, whereas with frameworks, they reuse        design. A framework embodies the way a family of related        programs or pieces of software work. It represents a generic        design solution that can be adapted to a variety of specific        problems in a given domain. For example, a single framework can        embody the way a user interface works, even though two different        user interfaces created with the same framework might solve        quite different interface problems.

Thus, through the development of frameworks for solutions to variousproblems and programming tasks, significant reductions in the design anddevelopment effort for software can be achieved. A preferred embodimentof the invention utilizes HyperText Markup Language (HTML) to implementdocuments on the Internet together with a general-purpose securecommunication protocol for a transport medium between the client and theNewco. HTTP or other protocols could be readily substituted for HTMLwithout undue experimentation. Information on these products isavailable in T. Berners-Lee, D. Connoly, “RFC 1866: Hypertext MarkupLanguage—2.0” (November 1995); and R. Fielding, H, Frystyk, T.Berners-Lee, J. Gettys and J. C. Mogul, “Hypertext TransferProtocol—HTTP/1.1: HTTP Working Group Internet Draft” (May 2, 1996).HTML is a simple data format used to create hypertext documents that areportable from one platform to another. HTML documents are SGML documentswith generic semantics that are appropriate for representing informationfrom a wide range of domains. HTML has been in use by the World-Wide Webglobal information initiative since 1990. HTML is an application of ISOStandard 8879; 1986 Information Processing Text and Office Systems;Standard Generalized Markup Language (SGML).

To date, Web development tools have been limited in their ability tocreate dynamic Web applications which span from client to server andinteroperate with existing computing resources. Until recently, HTML hasbeen the dominant technology used in development of Web-based solutions.However, HTML has proven to be inadequate in the following areas:

-   -   Poor performance;    -   Restricted user interface capabilities;    -   Can only produce static Web pages;    -   Lack of interoperability with existing applications and data;        and    -   Inability to scale.

Sun Microsystem's Java language solves many of the client-side problemsby:

-   -   Improving performance on the client side;    -   Enabling the creation of dynamic, real-time Web applications;        and    -   Providing the ability to create a wide variety of user interface        components.

With Java, developers can create robust User Interface (UI) components.Custom “widgets” (e.g., real-time stock tickers, animated icons, etc.)can be created, and client-side performance is improved. Unlike HTML,Java supports the notion of client-side validation, offloadingappropriate processing onto the client for improved performance.Dynamic, real-time Web pages can be created. Using the above-mentionedcustom UI components, dynamic Web pages can also be created.

Sun's Java language has emerged as an industry-recognized language for“programming the Internet.” Sun defines Java as: “a simple,object-oriented, distributed, interpreted, robust, secure,architecture-neutral, portable, high-performance, multithreaded,dynamic, buzzword-compliant, general-purpose programming language. Javasupports programming for the Internet in the form ofplatform-independent Java applets.” Java applets are small, specializedapplications that comply with Sun's Java Application ProgrammingInterface (API) allowing developers to add “interactive content” to Webdocuments (e.g., simple animations, page adornments, basic games, etc.).Applets execute within a Java-compatible browser (e.g., NetscapeNavigator) by copying code from the server to client. From a languagestandpoint, Java's core feature set is based on C++. Sun's Javaliterature states that Java is basically, “C++ with extensions fromObjective C for more dynamic method resolution.”

Another technology that provides similar function to JAVA is provided byMicrosoft and ActiveX Technologies, to give developers and Web designerswherewithal to build dynamic content for the Internet and personalcomputers. ActiveX includes tools for developing animation, 3-D virtualreality, video and other multimedia content. The tools use Internetstandards, work on multiple platforms, and are being supported by over100 companies. The group's building blocks are called ActiveX Controls,small, fast components that enable developers to embed parts of softwarein hypertext markup language (HTML) pages. ActiveX Controls work with avariety of programming languages including Microsoft Visual C++, BorlandDelphi, Microsoft Visual Basic programming system and, in the future,Microsoft's development tool for Java, code named “Jakarta.” ActiveXTechnologies also includes ActiveX Server Framework, allowing developersto create server applications. One of ordinary skill in the art readilyrecognizes that ActiveX could be substituted for JAVA without undueexperimentation to practice the invention.

FIG. 3 illustrates a home page interface 300 in accordance with oneembodiment of the present invention. As shown, a main menu 302 isdisplayed, which includes links to the main services of the childsupport system website. One link is to a Case Payment Information page(See also FIG. 12). Another is to a news page particular to the case ofthe user (See also FIG. 26). Also included on the home page interface isa supplemental links menu 304 which includes links to supplementalservices. A navigation bar 306, including a linked search page button308, a button 310 linked to a Frequently Asked Questions (FAQ) page, ahelp button 312, a contact page button 314, and site map button 316 canalso be provided to aid in navigation.

FIG. 4 is a flowchart illustrating a method 400 for affordinginformation services in a child support framework. First, in operation402, a database is provided including information relating to financialsupport. Such information includes a plurality of questions and answers.During use, the questions are displayed utilizing a network. Seeoperation 404. Further, in operation 406, a request is received from auser for the information relating to the financial support utilizing thenetwork. The request may include the selection of one of the questions.The answer corresponding to the selected question is then displayedutilizing the network. See operation 408.

In one embodiment of the present invention, the user may be linked toanother site on the network including information on financial supportfield offices. As an option, the information may relate to servicesprovided by a governmental financial support organization. Further, theinformation may relate to an eligibility for the services provided bythe governmental financial support organization, or identify financialsupport violators.

FIG. 5 is a graphical user interface 500 illustrating the frequentlyasked questions associated with the information services of FIG. 4 anddisplayed upon selection of the FAQ button on the home page. As shown,popular questions 502 which can be readily answered online are provided.Each question is linked to an answer section of the same page or anotherpage, where the answer to the question is displayed. Preferably, some ofthe questions and answers are directed towards preparing a user for atelephone or in-person interview with a case worker who will beassisting in the child support case.

FIG. 6 is a graphical user interface illustrating the financial supportviolators which is displayed upon selection of a most wanted link in thesupplemental link menu of the home page interface shown in FIG. 4. Asshown, a first column 602 displays names of the absent parents, whilesecond, third and fourth columns 604,606,608 display the absent parents'date of birth, last known address, and an amount of unpaid childsupport.

FIG. 7 is a graphical user interface 700 illustrating the field officelinks associated with the information services of FIG. 4 and displayedupon selection of a field office link in the supplemental link menu. Asshown, addresses, telephone numbers and email addresses are provided foreach of the field offices in the state.

FIG. 8 is a graphical user interface 800 illustrating other servicesassociated with the information services of FIG. 4. As shown, links torelated sites are provided. Such links can include links 802 directlyrelated to child support and links 804,806 indirectly related to childsupport.

FIG. 9 is a graphical user interface 900 illustrating a screen thatdisplays the eligibility requirements 902 associated with receivingfinancial support.

FIG. 10 is a flowchart illustrating a method 1000 for affording afinancial support payment status. First, in operation 1002, a databaseis established including information on a received financial supportpayment. The information may include an amount of the payment and a dateassociated with the payment. During use, a request is received from auser for the information on the received financial support paymentutilizing a network. See operation 1004. In response to the request, theinformation on the received financial support payment is displayedutilizing the network. Note operation 1006.

In one embodiment of the present invention, the date may include a datewhen the payment was received. Further, the date may include a date whenthe payment was sent to the user. An amount of time required for thereceived financial support payment to be available for withdrawal mayalso be displayed. In another embodiment of the present invention, theinformation may include a case number associated with the receivedfinancial support payment.

FIG. 11 is a graphical user interface 1100 displaying log-in fields1102,1104,1106 that may be required to be filled with user-specificinformation for execution of the method of FIG. 10. The log-in screenrestricts access to sensitive information such as case specifics,payment logs, payment forms, etc. A user identification number is placedin field 1102 and a personal identification number is placed in field1104 to verify authorization. The user then selects the CP submit button1108 if the user is the Custodial Parent (CP) or the NCP submit button1110 if the user is the Non-Custodial Parent (NCP) gain access to theprotected information.

FIG. 12 is a graphical user interface 1200 that allows access to varioustypes of status information in accordance with the method of FIG. 10. Asshown, links 1202 to case payment information are displayed. Selectionof the various links bring up screens displaying a current status of apayment, an amount due for a payment period, and a payment history.

FIG. 13 is a flowchart illustrating a method 1300 for providing apayment history of a financial support payment. Information regarding afinancial support payment from a non-custodial parent to a custodialparent is tracked utilizing a network. Note operation 1302. Then thetracking information is stored in a database in operation 1304. Thetracking information is subsequently stored utilizing the network inresponse to a request by the custodial parent. See operation 1306.

In an aspect of the invention, the tracking information can take theform of a chart. In another aspect of the invention the trackinginformation can be selected from the group consisting of a date, anamount received on the date, an amount retained of the amount received,and a disbursement of the amount received to the custodial parent. Instill another aspect of the invention, the network includes theInternet. In still yet another aspect of the invention, the trackinginformation is displayed only after a user logs in.

FIG. 14 is a graphical user interface 1400 that conveys the paymenthistory information in accordance with the method of FIG. 13. As shown,the date each payment received is displayed along with the amountreceived. The amount retained and the amount disbursed to the CustodialParent is also displayed.

FIG. 15 is a flowchart of a method 1500 for calculating an amount ofchild support. First, in operation 1502, data is received relating to atleast one of a non-custodial parent and a custodial parent utilizing anetwork. The data may include income, number of children, basic support,insurance premium, child care cost, and/or additional expenses. Duringuse, an amount of child support due based on the received data inoperation 1504. Such calculated amount of child support due is displayedutilizing the network, as indicated in operation 1506.

In one embodiment of the present invention, the data may be received byallowing a user to fill in a plurality of fields on a chart. Further, auser may be permitted to change a profile thereof in response to thedisplay of the calculated amount of child support due. Still yet, thedata may indicate whether a father or a mother is the custodial parent.

FIG. 16 is a graphical user interface 1600 that executes the calculatorfunction in accordance with the method of FIG. 15. The calculatorfunction is used to calculate an estimated amount of child support dueper period of time. As shown, the gross monthly incomes of both the CPand the NCP are entered in the gross monthly income fields 1602. A basicchild care amount is entered in the basic support field 1604. Additionalfields are provided to submit additional child care expenses. Uponentering the information, the Calculate Child Support button 1606 isselected to begin calculation. The approximate amount of child supportis displayed on a results screen (not shown).

FIG. 17 is a summary 1700 of a proposed site map associated with thepresent invention.

FIGS. 18-24 show flow diagrams illustrating possible navigation routesthe user can take during use of the present invention.

Most Wanted Page

This section describes the general design for the 25 Most Wanted Pagefor an electronic Child Support Enforcement Web Application (eCSE). Thisis achieved by providing an overview of the system's variousinfrastructure components and their interdependencies.

Objectives

The main objectives of this section is to:

-   -   Provide an overview of the all components and their dependencies        of the 25 Most Wanted Page.    -   Describe the 25 Most Wanted Page infrastructure objects in        sufficient detail to support their build.    -   Act as a reference guide for the 25 Most Wanted Page        infrastructure objects.        General Design Requirements

The eCSE 25 most wanted web page is designed to include thefunctionality required perform the following:

View the 25 Most Wanted Non-Custodial Parents online.

25 Most Wanted Components

Description

An Internet user using a certified web browser will request data from anHTML page.

Data will be retrieved from the SQL7 Server through the ICBAMArchitecture. The ICBAM Architecture was built using Microsoft ObjectComponent Technologies (COM).

Data will pass through the business logic using the page controller(COM) component to/from the Active Server Pages.

Active server pages will be used to display the top 25 most wantednon-Custodial parents who haven't pay their child support sorted fromthe highest outstanding balance to the lowest. Any errors encounteredduring the data retrieval will be documented in a server error log.

Data Input Sources

There are no user inputs required for the 25 Most Wanted Page. However,when user clicks on the 25 Most Wanted Link from the side menu to accessthe page, the page will retrieve the 25 Most Wanted data and displayback to the user on the web page.

Data Security

No security user logon is required.

Infrastructure Components

FIG. 25 illustrates the components of the “25 Most Wanted”Infrastructure. The infrastructure is comprised of the followingcomponents:

SQL7 Data Repository on Web Server 2500. An established area on theState web server where all files to be used by the eCSE SQL7 datawarehouse will be deposited.

Server Microsoft SQL7 Data Warehouse 2502. A robust relational databasecontaining tables with data necessary to encompass the functionality ofthe current State Child Support Enforcement system monthly process.

Client Web Browser Graphical User Interface 2504. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) whicha client (user) will use to enter new data from the client's web browserinto the appropriate sql server tables and generate requested resultsback to the client web browser.

25 Most Wanted Active Server Page (ASP) 2506. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) callson the 25 Most Wanted Active Server Page to display a list back to theclient browser of the top 25 non-custodial parents who has the highestoutstanding child support payments to date. The 25 Most Wanted activeserver page should contain the following:

-   -   Little logic except to interact with the 25 Most Wanted Page        Controller.    -   HTML code to display the results.    -   Client side scripting for common tasks such as formatting,        validation, etc.

25 Most Wanted Business Component 2508. The 25 Most Wanted BusinessComponent defines all of the public interfaces for the 25 most wantedbusiness related components. It is responsible for all the data accessto the SQL7 Server Database related to the 25 most wanted data. Inaddition, the 25 Most Wanted business component will contain thefollowing:

-   -   Majority of the business logic related to 25 most wanted page.    -   Implementation of all the well defined interfaces.    -   Calls of all backend Application Programmable Interfaces (API)        if necessary.    -   A Microsoft Transaction Server (MTS) Component.    -   Implementation of a declarative and/or programmatic security if        necessary.

The output result will display a list of the top 25 non-custodialparents who have the highest outstanding child support payments to dateback to the client's web browser.

25 Most Wanted Page Controller 2510. The 25 Most Wanted page controlleris a Microsoft Transaction Server (MTS) component that will provide astandard way of transporting data to and from the 25 Most Wanted ActiveServer Page through dictionary objects. It implements business logicthat would otherwise reside in the 25 most wanted active server page. Itis the co-ordinator between the interactions of the 25 Most Wanted ASPand the 25 Most Wanted Business Components. In addition, the 25 MostWanted Page Controller will interface with the Internet InformationServer event handlers.

ICBAM Architecture Component 2512. The Internet Component BasedArchitecture Model (ICBAM) component that will provide a the followingcommon architecture services:

-   -   Error handling    -   Logging Services    -   Database Access    -   ID Generation    -   Security Service    -   Registry Service    -   Text Service    -   State Maintenance        Data Validation Checks

The architecture component has error handling routines that ensure dataintegrity when retrieving data.

Required Output

Name of Absent Parent, Date of Birth, Last Known Address and the AmountOwed will be displayed from the 25 Most Wanted Active Server Page. Thedata is viewable online and printable.

Recent News on Case Display Page

This portion describes the general design for the Recent News on CaseDisplay Page for the electronic Child Support Enforcement WebApplication (eCSE). This is achieved by providing an overview of thesystem's various infrastructure components and their interdependencies.

Objectives

The main objectives of this section are to:

-   -   Provide an overview of the all components and their dependencies        of the Recent News on Case Page.    -   Describe the Recent News on Case Page infrastructure objects in        sufficient detail to support their build.    -   Act as a reference guide for the Recent News on Case display        Page infrastructure objects.        General Design Requirements

The eCSE Recent News on Case web page is designed to include thefunctionality required perform the following:

View the Recent News on Case web page online.

Recent News on Case Display Components

Description

Custodial Parent will click the Recent News on Case link from the HomePage using a certified web browser.

Custodial Parent must logon to their case account using the Logon Page.

Data will be requested from an HTML page by Custodial Parent's CaseNumber Link.

Data will be retrieved from the SQL7 Server through the ICBAMArchitecture. The ICBAM Architecture was built using Microsoft ObjectComponent Technologies (COM).

Data will pass through the business logic using the page controller(COM) component to/from the Active Server Pages.

Active server pages will be used to display information the Recent Newson Case as of current date. This includes any developments that occurthroughout the child support process. Any errors encountered during thedata retrieval will be documented in a server error log using the ICBAMArchitecture.

Data Input Sources

There are no user inputs required for the Recent News on Case Page.However, when Custodial Parent user clicks on the URL to access thepage, the page will retrieve the Recent News on Case data by the CaseNumber selected and display case news information back to the CustodialParent user's web browser.

Data Security

Social Security logon, and password is required. Please see LogonScreen/Security and Authentication general design for more details.

Infrastructure Components

FIG. 26 depicts an infrastructure of a system for displaying the RecentNews on Case. The infrastructure is comprised of the followingcomponents:

SQL7 Data Repository on Web Server 2600. An established area on the webserver where all files to be used by the eCSE SQL7 data warehouse willbe deposited.

Server Microsoft SQL7 Data Warehouse 2602. A robust relational databasecontaining tables with data necessary to encompass the functionality ofthe current Child Support Enforcement system monthly process.

Client Web Browser Graphical User Interface 2604. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) whicha Custodial Parent client (user) will use to click on a Case Number linkfrom the client's web browser to initiate querying the appropriate SQLserver tables and generate requested results back to the client webbrowser.

Recent News on Case Active Server Page (ASP) 2606. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) callson the Recent News on Case Active Server Page to display back to theclient browser the most recent information about the progress of a case.The Recent News on Case Active Server Page will contain the following:

Little logic except to interact with the Recent News on Case PageController.

HTML code to display the results.

Recent News on Case Business Component 2608. The Recent News on CaseBusiness Component defines all of the public interfaces for the RecentNews on Case business related components. It is responsible for all thedata access to the SQL7 Server Database related to the Recent News onCase data. In addition, the Recent News on Case Display businesscomponent will contain the following:

-   -   Majority of the business logic related to Recent News on Case        page.    -   Implementation of all the well defined interfaces.    -   Calls of all backend Application Programmable Interfaces (API)        if necessary.    -   A Microsoft Transaction Server (MTS) Component.

Implementation of a declarative and/or programmatic security ifnecessary. The output result will display a list of the top 25non-custodial parents who has the highest outstanding child supportpayments to date back to the client's web browser.

Recent News on Case Display Page Controller 2610. The Recent News onCase Page Controller is a Microsoft Transaction Server (MTS) componentthat will provide a standard way of transporting data to and from theRecent News on Case Active Server Page through dictionary objects. Itimplements business logic that would otherwise will reside in the RecentNews on Case Display active server page. It is the co-ordinator betweenthe interaction of the Recent News on Case Display ASP and the RecentNews on Case Display Business Components. In addition, the Recent Newson Case Page Controller will interface with the Internet InformationServer event handlers.

ICBAM Architecture Component 2612. The Internet Component BasedArchitecture Model (ICBAM) component that will provide a the followingcommon architecture services:

-   -   Error handling    -   Logging Services    -   Database Access    -   ID Generation    -   Security Service    -   Registry Service    -   Text Service    -   State Maintenance        Data Validation Checks

The architecture component has error handling routines while retrievingdata.

Required Output

A list of recent case action events related to the case number followedby month, date, and year of the action will be displayed from the RecentNews on Case Active Server Page. The said data will be viewable onlineand printable.

Amount Due for the Current Month Display Page

This portion describes the general design for the Amount Due For TheCurrent Month display Page for the electronic Child Support EnforcementWeb Application (eCSE). This is achieved by providing an overview of thesystem's various infrastructure components and their interdependencies.

Objectives

The main objectives of this section are to:

-   -   Provide an overview of the all components and their dependencies        of the Amount Due For The Current Month Page.    -   Describe the Amount Due For The Current Month Page        infrastructure objects in sufficient detail to support their        build.    -   Act as a reference guide for the Amount Due For The Current        Month Page infrastructure objects.        General Design Requirements

The eCSE Amount Due For The Current Month web page is designed toinclude the functionality required perform the following:

View the Amount Due For The Current Month web page online.

Amount Due for the Current Month Components

Description

Custodial Parent will click the Amount Due For The Current Month linklocated in the main menu selection bar in the Custodial Parent CasePayment Information Page using a certified web browser.

Data will be retrieved from the SQL7 Server through the ICBAMArchitecture. The ICBAM Architecture was built using Microsoft ObjectComponent Technologies (COM).

Data will pass through the business logic using the page controller(COM) component to/from the Active Server Pages.

Active server pages will be used to display the Amount Due For TheCurrent Month Information in a paragraph form. The data will display inthe form of three paragraphs:

The first paragraph displays as of last case process date, the amountthat the non-Custodial Parent owes the Custodial Parent, the amount thathas been paid to date, and the total amount still owed to CustodialParent.

The second paragraph displays the total of all past payments in arrearsthat the non-Custodial Parent owed to the Custodial Parent and thescheduled payment that the non-Custodial Parent owes the CustodialParent.

The third paragraph displays the combined total due/payable for thecurrent amount.

Any errors encountered during the data retrieval will be documented in aserver error log using the ICBAM Architecture.

Data Input Sources

There are no user inputs required for the Amount Due For The CurrentMonth Web Page. However, when the Custodial Parent logs on, access thecase payment information page and clicks on the Amount Due For TheCurrent Month link, the page will capture the following:

-   -   The non-custodial parent name.    -   The custodial parent name.    -   Case number.

The active server page will retrieve the Amount Due For The CurrentMonth data information formatted in three paragraphs back to theCustodial Parent user's web browser.

Data Security

Social Security logon, and password is required. Please see LogonScreen/Security and Authentication general design document for moredetails.

Infrastructure Components

The infrastructure is comprised of the following components, as shown inFIG. 27:

SQL7 Data Repository on Web Server 2700. An established area on the webserver where all files to be used by the eCSE SQL7 data warehouse willbe deposited.

Server Microsoft SQL7 Data Warehouse 2702. A robust relational databasecontaining tables with data necessary to encompass the functionality ofthe current Child Support Enforcement system monthly process.

Client Web Browser Graphical User Interface 2704. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) whicha Custodial Parent client (user) will use to click on a Case Number linkfrom the client's web browser to initiate querying the appropriate SQLserver tables and generate requested results back to the client webbrowser.

Amount Due For The Current Month Active Server Page (ASP) 2706. Theclient web based front-end of the application in Hyper Text MarkupLanguage (HTML) calls on the Amount Due For The Current Month ActiveServer Page to display back to the client browser the most recentinformation about the progress of receiving a payment. The Amount Duefor the Current Month Active Server Page will contain the following:

-   -   Little logic except to interact with the Amount Due For The        Current Month Page Controller.    -   HTML code to display the results.

Amount Due For The Current Month Business Component 2708. The Amount DueFor The Current Month Business Component defines all of the publicinterfaces for the Amount Due For The Current Month business relatedcomponents. It is responsible for all the data access to the SQL7 ServerDatabase related to the Amount Due For The Current Month data. Inaddition, the Amount Due For The Current Month business component willcontain the following:

-   -   Majority of the business logic related to Amount Due For The        Current Month page.    -   Implementation of all the well defined interfaces.    -   Calls of all backend Application Programmable Interfaces (API)        if necessary.    -   A Microsoft Transaction Server (MTS) Component.    -   Implementation of a declarative and/or programmatic security if        necessary.

The output result will display three paragraphs which contains the lastcase process date, the amount that the non-Custodial Parent owes theCustodial Parent, the amount that has been paid to date, the totalamount still owed to Custodial Parent, the total of all past payments inarrears that the non-Custodial Parent owed to the Custodial Parent andthe scheduled payment that the non-Custodial Parent owes the CustodialParent, and the combined total due/payable for the current amount backto the custodial parent's web browser.

Amount Due For The Current Month Page Controller 2710. The Amount DueFor The Current Month Page Controller is a Microsoft Transaction Server(MTS) component that will provide a standard way of transporting data toand from the Amount Due For The Current Month Active Server Page throughdictionary objects. It implements business logic that would otherwisereside in the Amount Due For The Current Month Active Server Page. It isthe co-ordinator between the interaction of the Amount Due For TheCurrent Month Active Server Pages and the Amount Due For The CurrentMonth Business Components. In addition, the Amount Due For The CurrentMonth Page Controller will interface with the Internet InformationServer event handlers.

ICBAM Architecture Component 2712. The Internet Component BasedArchitecture Model (ICBAM) component that will provide the followingcommon architecture services:

-   -   Error handling    -   Logging Services    -   Database Access    -   ID Generation    -   Security Service    -   Registry Service    -   Text Service    -   State Maintenance        Data Validation Checks

The architecture component has error handling routines while retrievingdata.

Required Output

A list of recent case action events related to the case number followedby month, date, and year of the action will be displayed from the AmountDue For The Current Month Active Server Page. The said data will beviewable online and printable. The Amount Due For The Current Monthdisplay format where the output results are stored in the < > areas.

Contact Us/Email Connection to Case Worker Display Page

This portion describes the general design for the Contact Us/EmailConnection to Case Worker Display Page for the electronic Child SupportEnforcement Web Application (eCSE). This is achieved by providing anoverview of the system's various infrastructure components and theirinterdependencies.

Objectives

The main objectives of this section are to:

-   -   Provide an overview of the all components and their dependencies        of the Contact Us/Email Connection to Case Worker Page.    -   Describe the Contact Us/Email Connection to Case Worker Page        infrastructure objects in sufficient detail to support their        build.    -   Act as a reference guide for the Contact Us/Email Connection to        Case Worker Page infrastructure objects.        General Design Requirements

The eCSE Contact Us/Email Connection to Case Worker web page is designedto include the functionality required perform the following:

View the Contact Us/Email Connection to Case Worker web page online.

Send an email correspondence from Internet user to a Case Worker online.

Contact Us/Email Connection to Case Worker Components

Description

Custodial Parent will click the Contact Us link located in the top menuselection bar in the Home Page using a certified web browser. TheContact Us link will be displayed throughout the Child SupportEnforcement Web Site.

Data will be retrieved from the SQL7 Server through the ICBAMArchitecture. The ICBAM Architecture was built using Microsoft ObjectComponent Technologies (COM).

Data will pass through the business logic using the page controller(COM) component to/from the Active Server Pages.

Active server pages will be used to display the Contact Us—case workeremail link Office phone, local and 800 toll-free, and mailing address.Any errors encountered during the data retrieval will be documented in aserver error log using the ICBAM Architecture.

Data Input Sources

There are no user inputs required for the Contact Us Web Page. However,when an Internet User clicks on the URL to access the page, the pagewill retrieve the Contact Us/Email Connection to Case Worker data by theCase Number selected and display case news information back to theCustodial Parent user's web browser.

Data Security

No security user logon is required.

Infrastructure Components

As shown in FIG. 28, the infrastructure is comprised of the followingcomponents:

SQL7 Data Repository on Web Server 2800. An established area on the webserver where all files to be used by the eCSE SQL7 data warehouse willbe deposited.

Server Microsoft SQL7 Data Warehouse 2802. A robust relational databasecontaining tables with data necessary to encompass the functionality ofthe current Child Support Enforcement system monthly process.

Client Web Browser Graphical User Interface 2804. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) whicha Custodial Parent client (user) will use to click on a Case Number linkfrom the client's web browser to initiate querying the appropriate SQLserver tables and generate requested results back to the client webbrowser.

Contact Us/Email Connection to Case Worker Active Server Page (ASP)2806. The client web based front-end of the application in Hyper TextMarkup Language (HTML) calls on the Contact Us/Email Connection to CaseWorker Active Server Page to display back to the client browser the mostrecent information about the progress of a case. The Contact Us/EmailConnection to Case Worker Active Server Page will contain the following:

-   -   Little logic except to interact with the Contact Us/Email        Connection to Case Worker Page Controller.    -   HTML code to display the results.

Contact Us/Email Connection to Case Worker Business Component 2808. TheContact Us/Email Connection to Case Worker Business Component definesall of the public interfaces for the Contact Us/Email Connection to CaseWorker business related components. It is responsible for all the dataaccess to the SQL7 Server Database related to the Contact Us/EmailConnection to Case Worker data. In addition, the Contact Us/EmailConnection to Case Worker Display business component will contain thefollowing:

-   -   Majority of the business logic related to Contact Us/Email        Connection to Case Worker page.    -   Implementation of all the well defined interfaces.    -   Calls of all backend Application Programmable Interfaces (API)        if necessary.    -   A Microsoft Transaction Server (MTS) Component.    -   Implementation of a declarative and/or programmatic security if        necessary.

Contact Us/Email Connection to Case Worker Display Page Controller 2810.The Contact Us/Email Connection to Case Worker Page Controller is aMicrosoft Transaction Server (MTS) component that will provide astandard way of transporting data to and from the Contact Us Case WorkerActive Server Page through dictionary objects. It implements businesslogic that would otherwise reside in the Contact Us Display activeserver page. It is the co-ordinator between the interaction of theContact Us Active Server Pages and the Contact Us Business Components.In addition, the Contact Us Page Controller will interface with theInternet Information Server event handlers.

ICBAM Architecture Component 2812. The Internet Component BasedArchitecture Model (ICBAM) component that will provide the followingcommon architecture services:

-   -   Error handling    -   Logging Services    -   Database Access    -   ID Generation    -   Security Service    -   Registry Service    -   Text Service    -   State Maintenance

TCP/IP Network 2814. Internet user will send an email correspondence2816 through the TCP/IP network to the State's email server into a caseworker's inbox.

Data Validation Checks

The architecture component has error handling routines while retrievingdata. For the email form, the email address in the To: field must be inthe standard email address format:

anyname@anybody.com

anyname@anybody.net

anyname@anybody.org

Required Output

A list of recent case action events related to the case number followedby month, date, and year of the action will be displayed from theContact Us/Email Connection to Case Worker Active Server Page. The datawill be viewable online and printable.

Have You Found the Non-Custodial Parent of My Children Display Page

This portion describes the general design for the Have You Found theNon-Custodial Parent of My Children display Page for electronic ChildSupport Enforcement Web Application (eCSE). This is achieved byproviding an overview of the system's various infrastructure componentsand their interdependencies.

Objectives

The main objectives of this document are to:

-   -   Provide an overview of the all components and their dependencies        of the Have You Found the Non-Custodial Parent of My Children        Page.    -   Describe the Have You Found the Non-Custodial Parent of My        Children Page infrastructure objects in sufficient detail to        support their build.    -   Act as a reference guide for the Have You Found the        Non-Custodial Parent of My Children Page infrastructure objects.        General Design Requirements

The eCSE Have You Found the Non-Custodial Parent of My Children web pageis designed to include the functionality required in performing thefollowing:

-   -   View the Have You Found the Non-Custodial Parent of My Children        web page online.    -   Link to the Help Manage Case Page.        Have You Found the Non-Custodial Parent of My Children        Components        Description

Custodial Parent will click the Have You Found the Non-Custodial Parentof My Children link located in the main menu selection bar in theCustodial Parent Case Payment Information Page using a certified webbrowser.

Data will be retrieved from the SQL7 Server through the CBAMArchitecture. The CBAM Architecture was built using Microsoft ObjectComponent Technologies (COM).

Data will pass through the business logic using the page controller(COM) component to/from the Active Server Pages.

Active server pages will be used to display the Have You Found theNon-Custodial Parent of My Children Information in a paragraph form. Thedata will display in the form of two paragraphs:

The first paragraph displays the as of last processed date,non-Custodial Parent's full name, and whether or not the non-custodialparent has been located.

The second paragraph displays a message which informs the CustodialParent to make sure the home and work addresses are correct. If there isnew information about the non-Custodial Parent, it will contain a linkto the Manage My Case Page.

Any errors encountered during the data retrieval will be documented in aserver error log using the CBAM Architecture.

Data Input Sources

There are no user inputs required for the Have You Found theNon-Custodial Parent of My Children Web Page. However, when theCustodial Parent logs on, access the case payment information page andclicks on the Have You Found the Non-Custodial Parent of My Childrenlink, the page will capture the following:

-   -   The non-custodial parent name.    -   The custodial parent name.    -   Case number.

The active server page will retrieve the Have You Found theNon-Custodial Parent of My Children data information formatted in twoparagraphs back to the Custodial Parent user's web browser.

Data Security

Social Security logon, and password is required. Please see LogonScreen/Security and Authentication general design document for moredetails.

Infrastructure Components

As illustrated in FIG. 29, the infrastructure is comprised of thefollowing components:

SQL7 Data Repository on Web Server 2900. An established area on the webserver where all files to be used by the eCSE SQL7 data warehouse willbe deposited.

Server Microsoft SQL7 Data Warehouse 2902. A robust relational databasecontaining tables with data necessary to encompass the functionality ofthe current Child Support Enforcement system monthly process.

Client Web Browser Graphical User Interface 2904. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) whicha Custodial Parent client (user) will use to click on a Case Number linkfrom the client's web browser to initiate querying the appropriate SQLserver tables and generate requested results back to the client webbrowser.

Have You Found the Non-Custodial Parent of My Children Active ServerPage (ASP) 2906. The client web based front-end of the application inHyper Text Markup Language (HTML) calls on the Have You Found theNon-Custodial Parent of My Children Active Server Page to display backto the client browser the most recent information about the reasons oflocating or not locating the non-Custodial Parent. The Have You Foundthe Non-Custodial Parent of My Children Active Server Page will containthe following:

-   -   Little logic except to interact with the Have You Found the        Non-Custodial Parent of My Children Page Controller.    -   HTML code to display the results.

Have You Found the Non-Custodial Parent of My Children BusinessComponent 2908. The Have You Found the Non-Custodial Parent of MyChildren Business Component defines all of the public interfaces for theHave You Found the Non-Custodial Parent of My Children business relatedcomponents. It is responsible for all the data access to the SQL7 ServerDatabase related to the Have You Found the Non-Custodial Parent of MyChildren data. In addition, the Have You Found the Non-Custodial Parentof My Children business component will contain the following:

-   -   Majority of the business logic related to Have You Found the        Non-Custodial Parent of My Children page.    -   Implementation of all the well defined interfaces.    -   Calls of all backend Application Programmable Interfaces (API)        if necessary.    -   A Microsoft Transaction Server (MTS) Component.    -   Implementation of a declarative and/or programmatic security if        necessary.

The output result will display two paragraphs which contains theCustodial Parent full name, Case Number, non-Custodial Parent full name,links to the Current Home Address and the non-Custodial EmployersAddress page back to the custodial parent's web browser.

Have You Found the Non-Custodial Parent of My Children Page Controller2910. The Have You Found the Non-Custodial Parent of My Children PageController is a Microsoft Transaction Server (MTS) component that willprovide a standard way of transporting data to and from the Have YouFound the Non-Custodial Parent of My Children Active Server Page throughdictionary objects. It implements business logic that would otherwisereside in the Have You Found the Non-Custodial Parent of My ChildrenActive Server Page. It is the co-ordinator between the interaction ofthe Have You Found the Non-Custodial Parent of My Children Active ServerPages and the Have You Found the Non-Custodial Parent of My ChildrenBusiness Components. In addition, the Have You Found the Non-CustodialParent of My Children Page Controller will interface with the InternetInformation Server event handlers.

CBAM Architecture Component 2912. The Component Based Architecture Model(CBAM) component that will provide the following common architectureservices:

-   -   Error handling    -   Logging Services    -   Database Access    -   ID Generation    -   Security Service    -   Registry Service    -   Text Service    -   State Maintenance        Data Validation Checks

The architecture component has error handling routines while retrievingdata.

Required Output

A list of recent case action events related to the case number followedby month, date, and year of the action will be displayed from the HaveYou Found the Non-Custodial Parent of My Children Active Server Page.The said data will be viewable online and printable.

Where is My Money Display Page

This portion describes the general design for the Where is My MoneyDisplay Page for the electronic Child Support Enforcement WebApplication (eCSE). This is achieved by providing an overview of thesystem's various infrastructure components and their interdependencies.

Objectives

The main objectives of this section are to:

-   -   Provide an overview of the all components and their dependencies        of the Where is My Money Page.    -   Describe the Where is My Money Page infrastructure objects in        sufficient detail to support their build.    -   Act as a reference guide for the Where is My Money Page        infrastructure objects.        General Design Requirements

The eCSE Where is My Money web page is designed to include thefunctionality required perform the following:

-   -   View the Where is My Money web page online.        Where is My Money Components        Description

Custodial Parent will click the Where is My Money link located in themain menu selection bar in the Custodial Parent Case Payment InformationPage using a certified web browser.

Data will be retrieved from the SQL7 Server through the ICBAMArchitecture. The ICBAM Architecture was built using Microsoft ObjectComponent Technologies (COM).

Data will pass through the business logic using the page controller(COM) component to/from the Active Server Pages.

Active server pages will be used to display the Where is My MoneyInformation in a paragraph form. The data will display the currentmonth's payment, The date the payment was mailed to the CustodialParent, When will the check be delivered, and an option link to set up adirect deposit into the Custodial Parent's account. Any errorsencountered during the data retrieval will be documented in a servererror log using the ICBAM Architecture.

Data Input Sources

There are no user inputs required for the Where is My Money Web Page.However, when an Internet User clicks on the Where is My Money link, thepage will retrieve the Where is My Money data in a paragraph back to theCustodial Parent user's web browser.

Data Security

Social Security logon, and password is required. Please see LogonScreen/Security and Authentication general design document for moredetails.

Infrastructure Components

The infrastructure is comprised of the following components, shown inFIG. 30:

SQL7 Data Repository on Web Server 3000. An established area on the webserver where all files to be used by the eCSE SQL7 data warehouse willbe deposited.

Server Microsoft SQL7 Data Warehouse 3002. A robust relational databasecontaining tables with data necessary to encompass the functionality ofthe current Child Support Enforcement system monthly process.

Client Web Browser Graphical User Interface 3004. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) whicha Custodial Parent client (user) will use to click on a Case Number linkfrom the client's web browser to initiate querying the appropriate SQLserver tables and generate requested results back to the client webbrowser.

Where is My Money Active Server Page (ASP) 3006. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) callson the Where is My Money Active Server Page to display back to theclient browser the most recent information about the progress ofreceiving a payment. The Where is My MoneyActive Server Page willcontain the following:

-   -   Little logic except to interact with the Where is My Money Page        Controller.    -   HTML code to display the results.

Where is My Money Business Component 3008. The Where is My MoneyBusiness Component defines all of the public interfaces for the Where isMy Money business related components. It is responsible for all the dataaccess to the SQL7 Server Database related to the Where is My Moneydata. In addition, the Where is My Money business component will containthe following:

-   -   Majority of the business logic related to Where is My Money        page.    -   Implementation of all the well defined interfaces.    -   Calls of all backend Application Programmable Interfaces (API)        if necessary.    -   A Microsoft Transaction Server (MTS) Component.    -   Implementation of a declarative and/or programmatic security if        necessary.

The output result will display a paragraph of the amount of money, thedate the money was mailed back to the custodial parent's web browser.

Where is My Money Page Controller 3010. The Where is My Money PageController is a Microsoft Transaction Server (MTS) component that willprovide a standard way of transporting data to and from the Where is MyMoney Active Server Page through dictionary objects. It implementsbusiness logic that would otherwise will reside in the Where is My MoneyActive Server Page. It is the co-ordinator between the interaction ofthe Where is My Money Active Server Pages and the Where is My MoneyBusiness Components. In addition, the Where is My Money Page Controllerwill interface with the Internet Information Server event handlers.

ICBAM Architecture Component 3012. The Internet Component BasedArchitecture Model (ICBAM) component that will provide the followingcommon architecture services:

-   -   Error handling    -   Logging Services    -   Database Access    -   ID Generation    -   Security Service    -   Registry Service    -   Text Service    -   State Maintenance        Data Validation Checks

The architecture component has error handling routines while retrievingdata.

Required Output

A list of recent case action events related to the case number followedby month, date, and year of the action will be displayed from the Whereis My Money Active Server Page. The said data will be viewable onlineand printable. The Where is My Money display format where the outputresults are stored in the < > areas.

Why Didn't I Get My Child Support Payment Display Page

This portion describes the general design for the Why Didn't I Get MyChild Support Payment display Page for the electronic Child SupportEnforcement Web Application (eCSE). This is achieved by providing anoverview of the system's various infrastructure components and theirinterdependencies.

Objectives

The main objectives of this document are to:

-   -   Provide an overview of the all components and their dependencies        of the Why Didn't I Get My Child Support Payment Page.    -   Describe the Why Didn't I Get My Child Support Payment Page        infrastructure objects in sufficient detail to support their        build.    -   Act as a reference guide for the Why Didn't I Get My Child        Support Payment Page infrastructure objects.        General Design Requirements

The eCSE Why Didn't I Get My Child Support Payment web page is designedto include the functionality required perform the following:

-   -   View the Why Didn't I Get My Child Support Payment web page        online.    -   Link to update the current Home Address of the non-Custodial        and/or Custodial Parent.    -   Link to update the Employer's Address of the non-Custodial        Parent.        Why Didn't I Get My Child Support Payment Components        Description

Custodial Parent will click the Why Didn't I Get My Child SupportPayment link located in the main menu selection bar in the CustodialParent Case Payment Information Page using a certified web browser.

Data will be retrieved from the SQL7 Server through the ICBAMArchitecture. The ICBAM Architecture was built using Microsoft ObjectComponent Technologies (COM).

Data will pass through the business logic using the page controller(COM) component to/from the Active Server Pages.

Active server pages will be used to display the Why Didn't I Get MyChild Support Payment Information in a paragraph form. The data willdisplay in the form of two paragraphs:

The first paragraph displays the reason the payment was not received,and the non-Custodial Parent's full name.

The second paragraph displays a message which informs the CustodialParent to make sure the current address is correct. In addition, thesecond paragraph will contain the links to the Current Address Page andCurrent Employers Address Page of the non-Custodial Parent.

Any errors encountered during the data retrieval will be documented in aserver error log using the ICBAM Architecture.

Data Input Sources

There are no user inputs required for the Why Didn't I Get My ChildSupport Payment Web Page. However, when the Custodial Parent logs on,access the case payment information page and clicks on the Why Didn't IGet My Child Support Payment link, the page will capture the following:

-   -   The non-custodial parent name.    -   The custodial parent name.    -   Case number.

The active server page will retrieve the Why Didn't I Get My ChildSupport Payment data information formatted in two paragraphs back to theCustodial Parent user's web browser.

Data Security

Social Security logon, and password is required. Please see LogonScreen/Security and Authentication general design document for moredetails.

Infrastructure Components

The infrastructure is comprised of the following components:

SQL7 Data Repository on Web Server 3100. An established area on the webserver where all files to be used by the eCSE SQL7 data warehouse willbe deposited.

Server Microsoft SQL7 Data Warehouse 3102. A robust relational databasecontaining tables with data necessary to encompass the functionality ofthe current Child Support Enforcement system monthly process.

Client Web Browser Graphical User Interface 3104. The client web basedfront-end of the application in Hyper Text Markup Language (HTML) whicha Custodial Parent client (user) will use to click on a Case Number linkfrom the client's web browser to initiate querying the appropriate SQLserver tables and generate requested results back to the client webbrowser.

Why Didn't I Get My Child Support Payment Active Server Page (ASP) 3106.The client web based front-end of the application in Hyper Text MarkupLanguage (HTML) calls on the Why Didn't I Get My Child Support PaymentActive Server Page to display back to the client browser the most recentinformation about the reasons of not receiving a payment. The Why Didn'tI Get My Child Support Payment Active Server Page will contain thefollowing:

-   -   Little logic except to interact with the Why Didn't I Get My        Child Support Payment Page Controller.    -   HTML code to display the results.

Why Didn't I Get My Child Support Payment Business Component 3108. TheWhy Didn't I Get My Child Support Payment Business Component defines allof the public interfaces for the Why Didn't I Get My Child SupportPayment business related components. It is responsible for all the dataaccess to the SQL7 Server Database related to the Why Didn't I Get MyChild Support Payment data. In addition, the Why Didn't I Get My ChildSupport Payment business component will contain the following:

-   -   Majority of the business logic related to Why Didn't I Get My        Child Support Payment page.    -   Implementation of all the well defined interfaces.    -   Calls of all backend Application Programmable Interfaces (API)        if necessary.    -   A Microsoft Transaction Server (MTS) Component.    -   Implementation of a declarative and/or programmatic security if        necessary.

The output result will display two paragraphs which contains theCustodial Parent full name, Case Number, non-Custodial Parent full name,links to the Current Home Address and the non-Custodial EmployersAddress page back to the custodial parent's web browser.

Why Didn't I Get My Child Support Payment Page Controller 3110. The WhyDidn't I Get My Child Support Payment Page Controller is a MicrosoftTransaction Server (MTS) component that will provide a standard way oftransporting data to and from the Why Didn't I Get My Child SupportPayment Active Server Page through dictionary objects. It implementsbusiness logic that would otherwise will reside in the Why Didn't I GetMy Child Support Payment Active Server Page. It is the co-ordinatorbetween the interaction of the Why Didn't I Get My Child Support PaymentActive Server Pages and the Why Didn't I Get My Child Support PaymentBusiness Components. In addition, the Why Didn't I Get My Child SupportPayment Page Controller will interface with the Internet InformationServer event handlers.

ICBAM Architecture Component 3112. The Internet Component BasedArchitecture Model (ICBAM) component that will provide the followingcommon architecture services:

-   -   Error handling    -   Logging Services    -   Database Access    -   ID Generation    -   Security Service    -   Registry Service    -   Text Service    -   State Maintenance        Data Validation Checks

The architecture component has error handling routines while retrievingdata.

Required Output

A list of recent case action events related to the case number followedby month, date, and year of the action will be displayed from the WhyDidn't I Get My Child Support Payment Active Server Page. The said datawill be viewable online and printable.

Although only a few embodiments of the present invention have beendescribed in detail herein, it should be understood that the presentinvention may be embodied in many other specific forms without departingfrom the spirit or scope of the invention. Therefore, the presentexamples and embodiments are to be considered as illustrative and notrestrictive, and the invention is not to be limited to the details givenherein, but may be modified within the scope of the appended claims.

1. A method, implemented using a computer, for providing a network-basedchild financial support framework, the method comprising the steps of:maintaining a network database including information on a receivedfinancial support payment; calculating, using the computer, a properamount of the financial support payment based on a user profile and anamount paid to date from a non-custodial parent to a custodial parent,wherein the user profile includes data relating to at least one ofincome, number of children, basic support, insurance premium, child carecost, and additional expenses; receiving identification information fromthe user; determining, from the identification information, whether theuser is the custodial parent; and providing, only after determining theuser is the custodial parent, access to an interface configured to allowthe custodial parent to retrieve tracking information for the financialsupport payment, said tracking information including at least one ofpayment status, payment amount due, payment amount received, paymentdate, and payment available withdrawal date.
 2. The method as recited inclaim 1, wherein the method is implemented using a network that includesthe Internet.
 3. The method as recited in claim 1, further comprising:allowing, only after determining the user is the custodial parent, theuser to change at least a portion of the data in the user profile. 4.The method as recited in claim 1, wherein the interface is furtherconfigured to allow the custodial parent to retrieve trackinginformation for the financial support payment and history data relatingto a plurality of historical financial support payments.
 5. The methodas recited in claim 1, wherein the history data includes a date, anamount received on the date, an amount retained of the amount received,and a disbursement of the amount received to the custodial parent.
 6. Asystem for providing a network-based child financial support framework,the system comprising: a central processing unit; a memory unit incommunication with the central processing unit; one or more modulesthat: maintains a network database including information on a receivedfinancial support payment; calculates a proper amount of the financialsupport payment based on a user profile and an amount paid to date froma non-custodial parent to a custodial parent, wherein the user profileincludes data relating to at least one of income, number of children,basic support, insurance premium, child care cost, and additionalexpenses; receives identification information from the user; determines,from the identification information, whether the user is the custodialparent; and provides, only after determining the user is the custodialparent, access to an interface configured to allow the custodial parentto retrieve tracking information for the financial support payment, saidtracking information including at least one of payment status, paymentamount due, payment amount received, payment date, and payment availablewithdrawal date.
 7. The system as recited in claim 6, further comprisinga network that includes the Internet.
 8. The system as recited in claim6, wherein: the one or more modules allows, only after determining theuser is the custodial parent, the user to change at least a portion ofthe data in the user profile.
 9. The system as recited in claim 6,wherein the interface is further configured to allow the custodialparent to retrieve tracking information for the financial supportpayment and history data relating to a plurality of historical financialsupport payments.
 10. The system as recited in claim 6, wherein thehistory data includes a date, an amount received on the date, an amountretained of the amount received, and a disbursement of the amountreceived to the custodial parent.
 11. A computer-readable mediumincluding a computer program encoded thereon which, when executed,causes a computer to perform a method for providing a network-basedchild financial support framework, the method comprising the steps of:maintaining a network database including information on a receivedfinancial support payment; calculating, using the computer, a properamount of the financial support payment based on a user profile and anamount paid to date from a non-custodial parent to a custodial parent,wherein the user profile includes data relating to at least one ofincome, number of children, basic support, insurance premium, child carecost, and additional expenses; receiving identification information fromthe user; determining, from the identification information, whether theuser is the custodial parent; and providing, only after determining theuser is the custodial parent, access to an interface configured to allowthe custodial parent to retrieve tracking information for the financialsupport payment, said tracking information including at least one ofpayment status, payment amount due, payment amount received, paymentdate, and payment available withdrawal date.
 12. The computer-readablemedium as recited in claim 11, wherein the network includes theInternet.
 13. The computer-readable medium as recited in claim 11,wherein the method further comprising: allowing, only after determiningthe user is the custodial parent, the user to change at least a portionof the data in the user profile.
 14. The computer-readable medium asrecited in claim 11, wherein the interface is further configured toallow the custodial parent to retrieve tracking information for thefinancial support payment and history data relating to a plurality ofhistorical financial support payments.
 15. The computer-readable mediumas recited in claim 11, wherein the history data includes a date, anamount received on the date, an amount retained of the amount received,and a disbursement of the amount received to the custodial parent.